Voucher system and method of use

ABSTRACT

A system for managing voucher use includes a database, a voucher, and a processor. The database stores an account defining at least one approved item available for purchase and a financial balance. The voucher includes an identifier linking the voucher to the account. The processor is in communication with the database and is adapted to use the identifier to access the account. The processor is adapted to determine if an item selected for purchase is an approved item and to apply at least a portion of the financial balance toward the purchase of the selected item only if the selected item is an approved item. Other voucher systems and associated methods are also disclosed.

BACKGROUND OF THE INVENTION

Relief agencies and other organizations are a source of comfort andassistance to individuals and families in times of need. One type ofassistance commonly provided by relief agencies is financial assistance.For instance, certain relief agencies provide recipients with vouchersfor use as payment for food, clothing, and other necessities at one ormore retail stores, markets, or special relief outlets. Conventionalvouchers are not provided in any particular physical format. Somevouchers may be printed on a small paperboard card while others areprinted on a letter-size piece of paper. Vouchers generally are printedwith a monetary value for which the voucher can be redeemed and areassociated with a list of approved products that can be purchased withthe voucher and/or restricted products that cannot be purchased with thevoucher.

During use, recipients typically present vouchers to a cashier at thepoint-of-sale (POS) terminal of a retail or other redemption site eitherbefore, during, or after a plurality of items have been processed forsale. The cashier first attempts to verify the validity of the voucher,which is often complicated by the lack of physical uniformity in thevouchers. Once the voucher is verified, the cashier examines each itembeing purchased and determines if a particular voucher can be appliedtoward the purchase of that item (i.e., the employee must determine ifthe items are approved or restricted items). This task is complicated inmixed transactions in which the voucher can be applied toward some butnot all of the products being purchased in a single transaction.

Cashiers also police use of the voucher only for purchases up to theamount specified on the voucher. For instance, if the voucher is for$100 in food supplies, the cashier polices the transaction to be surethe voucher is not applied to cover all of a $102 food supply purchase.In view of the above, the cashier is required to enforce any voucherterms of use defined by the issuing relief agency. However, by requiringcashiers to enforce voucher terms of use in addition to their typicalduties and in view of the number of variables to be policed, theopportunities for errors in processing the vouchers, and the recipienttime spent at the POS terminal during check-out, increase.

In addition, relief agencies typically require an accounting of whatitems were purchased with the vouchers. In one conventional vouchersystem, such accountability requires a cashier to obtain a bar code orother identifier corresponding to the relief agency that provided thevoucher. The identifier is entered into the POS terminal along with aserial number of the particular voucher being used to pay for at least aportion of the purchase. This act once again relies on the cashier tofind and select the appropriate relief agency identifier and to properlyenter all related information into the POS terminal. Not only does thisprovide additional opportunities for error, but it also delays thecheck-out process, which may frustrate the recipient as well as otherconsumers waiting to process their purchases at the POS terminal.

SUMMARY OF THE INVENTION

One aspect of the present invention provides a system for managingvoucher use. The system includes a database, a voucher, and a processor.The database stores an account defining at least one approved itemavailable for purchase and a financial balance. The voucher includes anidentifier linking the voucher to the account. The processor is incommunication with the database and is adapted to use the identifier toaccess the account. The processor is adapted to determine if an itemselected for purchase is an approved item and to apply at least aportion of the financial balance toward the purchase of the selecteditem only if the selected item is an approved item. Other relatedproducts, systems, and methods are also disclosed and provide additionaladvantages.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention will be described with respect to thefigures, in which like reference numerals denote like elements, and inwhich:

FIG. 1 is a block diagram illustrating one embodiment of a vouchersystem, according to the present invention.

FIG. 2 is a block diagram of a redemption organization of the vouchersystem of FIG. 1.

FIG. 3 is a schematic illustration of one embodiment of a voucher andassociated voucher account, according to the present invention.

FIG. 4 is a flow chart illustrating one embodiment of a method ofdistributing vouchers.

FIG. 5 is a flow chart illustrating one embodiment of a method ofredeeming vouchers.

FIG. 6 is a flow chart illustrating one embodiment of a method ofmanaging voucher use as supported by a redemption organization of FIG.1.

FIG. 7 is a block diagram illustrating one embodiment of a vouchersystem, according to the present invention.

DETAILED DESCRIPTION

Relief or other distribution agencies distribute financial transactioninstruments or vouchers to needy recipients for use toward purchases ofgoods and/or services from a retail store or other redemption site. Inone embodiment, the voucher takes the form of a stored-value cardadapted for making purchases of goods and/or services from e.g. a retailstore or website. The voucher includes an account identifier, such as abar code, a magnetic strip, and/or a radio frequency identificationdevice (RFID) tag, that links the voucher to an account. In oneembodiment, the account specifies a particular distribution agency thatprovided the voucher, an available balance or value of the voucher, andwhich items are approved (i.e. which items can be purchased with thevoucher). The account is electronically accessible via the accountidentifier and permits electronic enforcement of voucher terms of use asdefined by the distribution agency.

For example, in one embodiment, the retail store or other redemptionorganization is configured to process a transaction for sale of goodsand/or services at the point-of-sale (POS) terminal and to scan orotherwise enter the account identifier included on the voucher. Uponscanning the account identifier, the POS terminal and associated networkis configured to electronically determine whether each item beingpurchased falls within the approved and/or restricted items list definedin the associated voucher account and to apply the available balancetoward the purchase of the approved and non-restricted items. Since theredemption parameters of the stored-value card (i.e., the availablebalance and list of approved/restricted items) are electronicallyprocessed by the POS terminal rather than by the associated cashier, therisk of error in processing the voucher and the time required to processa purchase using the voucher are greatly diminished.

In one embodiment, the POS terminal is linked to a redemptionorganization network that is configured to log use of the stored-valuecard and to report detailed lists of voucher use to the distributionagency. In this manner, the distribution agency is able to track whichdistributed vouchers have been redeemed, what the redeemed vouchers havebeen used to purchase, and/or whether any residual balances remain onthe vouchers. In one example, the distribution agency is able to accesssuch tracking information, to order additional vouchers, and/or tomanage voucher accounts via a network, such as the Internet.

Components of the voucher systems described below and employed to carryout the methods described below can be implemented in hardware via amicroprocessor, programmable logic, or state machine, in firmware or insoftware with a given device. In one aspect, at least a portion of thesoftware programming is web-based and written in Hyper Text Mark-upLanguage (HTML) and/or Java programming languages, including links touser interfaces for data collection, such as a Windows based operatingsystem. Each of the main components may communicate via a network usinga communication bus protocol. For example, the present invention may usea Transmission Control Protocol/Internet Protocol (TCP/IP) suite fordata transport. Other programming languages and communication busprotocols are suitable for use to support methods described herein andwill become apparent to those skilled in the art after reading thisdisclosure. Components of the present invention may also reside insoftware on one or more computer-readable mediums. The term“computer-readable medium” as used herein is defined to include any kindof memory, whether volatile or non-volatile such as floppy disk, harddisk, CD-ROMs, flash memory, read-only memory (ROM) and random accessmemory (RAM).

Turning to the figures, FIG. 1 illustrates a block diagram of a vouchersystem 10 including a distribution agency 12, a voucher recipient 14,and a redemption organization 16. Distribution agency 12 is any partythat provides financial assistance in the form of vouchers to recipients14. In one embodiment, distribution agency 12 is a relief agency such asa homeless shelter, the Red Cross, the Salvation Army, the FederalEmergency Management Agency (FEMA), a state department of health, orother relief agency that distributes vouchers to recipients 14 that arevictims of poverty, natural disasters, and/or other compromising oremergency situations.

Redemption organization 16 is any site or network of sites adapted toaccept the vouchers as payment for items such as goods and/or servicespurchased by the recipients 14. One embodiment of redemptionorganization 16 is more particularly illustrated in FIG. 2. Redemptionorganization 16 includes approved items 20 for purchase, a POS terminal22 configured to process purchases made with vouchers, a managementdatabase 24, and a database processor or controller 26.

In one embodiment, approved items 20 and POS terminal 22 are eachincluded in a redemption site 30 within redemption organization.Redemption site 30 is any retail or wholesale outlet configured toredeem a voucher in exchange for approved items 20. POS terminal 22includes a reader 28 configured to read an identifier on the voucher anda processor or controller 29 configured to determine if the items 20being purchased are approved by the distribution agency 12 and to redeemthe value of the voucher toward the purchase of any approved items 20.Reader 28 is one example of means for reading an identifier of thevoucher. In one embodiment, a plurality of redemption sites 30 areincluded within redemption organization 16.

In one embodiment, redemption organization 16 is additionally configuredto supply distribution agency 12 with vouchers to distribute torecipients 14 and to support voucher issuance and management. In oneexample, management database 24 and database processor 26 are part of avoucher administrator 38 included within redemption organization 16.Management database 24 includes data for tracking and managing voucheruse. Database processor 26 is coupled with management database 24 and isadapted to processing information stored and to be stored in managementdatabase 24.

In one embodiment, management database 24 includes a voucher accountstorage module 32, a distribution agency profile storage module 34,and/or a generated reports storage module 36. Voucher account storagemodule 32 stores a plurality of voucher accounts, which are each linkedto a voucher. Each voucher account specifies a balance for theassociated voucher as well as the voucher terms of use as will befurther described below. Distribution agency profile storage module 34includes information regarding distribution agency 12 for managingvouchers distributed by distribution agency 12 such as contact andfinancial information for distribution agency 12. Generated reportstorage module 36 stores any voucher use reports, bills, etc. previouslygenerated by redemption organization 16 for distribution to distributionagency 12 by processor 26.

Referring once again to FIG. 1, distribution agency 12 is incommunication with recipients 14 and provides a voucher to eachrecipient 14 for use toward the purchase of items defined as approved bydistribution agency 12. For example, the voucher may be designated asapproved for the purchase of one or more item of clothing, food, etc.and/or designated as not approved for the purchase of alcohol, tobacco,electronics, etc. Recipient 14 subsequently takes the voucher to aretail or other redemption site 30 (FIG. 2) operated by redemptionorganization 16 for use toward the purchase of approved items.

In one embodiment, redemption organization 16 accepts the voucher aspayment only toward approved and non-restricted items. In addition,redemption organization 16 electronically tracks the purchase(s) made byrecipient 14 utilizing the voucher and provides data regarding vouchertransactions to distribution agency 12. In one embodiment, redemptionorganization 16 communicates with and/or otherwise makes informationavailable to distribution agency 12 via a network 18, such as theInternet. Although illustrated as including one distribution agency 12,one recipient 14, and one redemption organization 16, it should beunderstood that, in one embodiment, a plurality of distribution agencies12, a plurality of recipients 14, and/or a plurality of redemptionorganizations 16 are included in voucher system 10.

As illustrated in FIG. 3, in one embodiment, a financial transactioninstrument or voucher 40 is a stored-value card or other financialtransaction card. In one embodiment, voucher 40 includes printed matter42 or other indicia identifying what distribution agency 12 distributedvoucher 40, printed matter or other indicia 44 designating a redemptionorganization 16 configured to redeem voucher 40, and an accountidentifier 46. Account identifier 46 links voucher 40 to an associatedvoucher account 50. Account identifier 46 includes at least one of a barcode, a magnetic strip, a radio frequency identification device (RFID)tag, or other suitable link to account 50. In one embodiment, account 50is maintained by redemption organization 16 within voucher accountstorage module 32 (FIG. 2) and includes information regarding voucher40. In one embodiment, voucher 40 is any stored-value card or other itemincluding account identifier 46 configured to electronically linkvoucher 40 to account 50.

Account 50 includes various information fields 52 such as a distributionagency identification field 54, a voucher status field 56, a financialbalance field 58, an approved items field 60, an expiration date field62, a recipient identification data field 64, and/or a transactiondetails field 66. In one embodiment, account 50 includes alternative oradditional information, such as a particular redemption site at whichvoucher 40 can be redeemed, a designation of voucher 40 as a one-timeuse card, etc. In one embodiment, fields 52 facilitate redemptionorganization 16 in redeeming voucher 40 and distribution agency 12 inmonitoring use of vouchers 40 as will be further described below.

Voucher status field 56 designates whether voucher 40 is activated ornon-activated. Activated vouchers 40 can be used toward the purchase ofitems, whereas non-activated vouchers 40 cannot be used toward thepurchase of items. In one embodiment, distribution agency 12 receivesnon-activated vouchers 40 from redemption organization 16. Distributionagency 12 activates vouchers 40 as needed prior to the distribution ofvoucher 40 to recipient 14. By maintaining a majority of vouchers 40stored by distribution agency 12 as non-activated, the motivation fortheft of such vouchers from distribution agency 12 is decreased. In oneembodiment, other account fields 52 such as financial balance field 58,approved items field 60, and expiration date field 62 are unpopulateduntil after activation and/or use of voucher 40.

The financial balance field 58 indicates the current value of voucher40. In one embodiment, non-activated vouchers 40 have a financialbalance of zero dollars. In one embodiment, non-activated vouchers 40alternatively have a preset financial balance of $100, $150, $500, etc.However, if voucher 40 is non-activated, any financial balance inaccount 50 is not generally accessible for use toward the purchase ofitems. In one embodiment, the financial balance is specified bydistribution agency 12 during activation of voucher 40.

In one embodiment, when an activated voucher 40 is distributed torecipient 14, the financial balance is equal to the initial balanceadded to voucher 40 by distribution agency 12, for example, $500. Asvoucher 40 is redeemed for purchases, the financial balance isautomatically updated by POS terminal 22. For example, if voucher 40 isredeemed for $150 in food items, financial balance field 58 is updatedto indicate a remaining balance of $350, and so on. In one embodiment,additional value can be added or “loaded” onto voucher 40. In suchinstances, financial balance field 58 is updated, more particularly, isincreased, to indicate additional available funds to recipient 14. Inone example, distribution agency 12 adds a predetermined value tovoucher 40 after the expiration of a given time period. For instance,distribution agency 12 may add an amount such as $200 to voucher 40, andtherefore, updates financial balance field 58, at the end of each monthor other time period.

Approved items field 60 defines the subset of items for which voucher 40can be applied to purchase. In one example, approved items field 60 maydesignate individual items, items types, and/or departments of itemsthat voucher 40 can or cannot be used to purchase. In one embodiment,approved items field 60 designates approved items using a categoricaldistinction referring to the type of distribution being offered (i.e.food, clothing, food and clothing, etc.) wherein the redemptionorganization automatically equates the categorical distinction withparticular types of items available in its stores. In one embodiment,approved items field 60 defines approved items as items not included ina stored list of restricted items. For example, if a list of restricteditems only includes alcohol, tobacco, and electronics items, any food orclothing item would be an approved item since such items are notincluded in the list of restricted items.

In one embodiment, account 50 includes an expiration date field 62.Expiration date field 62 indicates a date or other occurrence upon whichvoucher 40 can no longer be redeemed. In one embodiment, following theexpiration date, distribution agency 12 may recapture any residualbalance on voucher 40. In one embodiment, expiration date field 62includes any other information regarding when the residual balance, ifany, on voucher 40 can be reclaimed by distribution agency 12. In otherembodiments, account 50 does not include expiration date field 62.

In one embodiment, account 50 includes recipient identification field64. Recipient identification field 64 includes information such as aname, address, driver's license number, social security number, etc.Recipient identification field 64 simplifies tracking of an individualrecipient's use of voucher 40. In one embodiment, recipientidentification field 64 is useful in decreasing abuse of vouchers 40.For example, during attempted redemption of voucher 40 as at leastpartial payment for one or more items, a cashier or other redemptionorganization employee may ask the current card bearer for someidentifying information, compare the card bearer response to storedrecipient information field 64. If the card bearer response matches thedata in recipient information field 64, the card bearer is identified asthe rightful recipient (i.e., the party given voucher 40 by distributionagency 12). If the voucher bearer is the rightful recipient, thenvoucher redemption continues; if the voucher bearer is not the rightfulrecipient, then voucher redemption is prevented. Accordingly, misuse andmisappropriation of voucher 40 can be decreased.

Transaction detail field 66 is typically blank or indicates that nodetail is available for non-activated vouchers 40 and for activatedvouchers 40 that have not yet been redeemed toward the purchase of anitem. Following redemption of an activated voucher 40, transactiondetail field 66 is populated with details regarding when, where, and onwhat voucher 40 was redeemed. In one embodiment, transaction detailfield 66 lists either specific product information, such as the size,brand, style, etc. of the item purchased (i.e., size 9, Brand X, bootcut jeans), or more general information identifying the item purchased(i.e., women's jeans) purchased at least in part with voucher 40.Subsequent redemptions of voucher 40, if any, further update transactiondetail field 66 with similar details of additional items purchased atleast in part with voucher 40.

FIG. 4 is a flow chart illustrating one embodiment of a method ofdistributing vouchers generally at 400, which is described below withrespect to FIGS. 1 and 3. At 402, distribution agency 12 obtains one ormore non-activated vouchers 40. In one embodiment, distribution agency12 manufactures vouchers, is issued vouchers 40 from redemptionorganization 16, or otherwise obtains vouchers 40. Vouchers 40 obtainedat 402 generally are already linked to account 50 via account identifier46. In one embodiment, one or more account fields 52 are populated upondistribution agency 12 obtaining voucher 40. For example, distributionagency field 54 is populated with the name of the particulardistribution agency 12, such as the Red Cross, the Salvation Army, FEMA,a state department of health, etc.

At 404, distribution agency 12 activates one or more vouchers 40 to bedistributed to recipients 14. During activation, distribution agency 12accesses and populates account fields to ready account 50 for voucheruse. In one embodiment, distribution agency 12 specifies a value forfinancial balance field 58, identifies approved items for field 60populates expiration field 62 and/or populates recipient data field 64.In one embodiment, approved items field 60 includes a listing ofindividual approved item types, specifies approved item categories,lists restricted items, and/or specifies restricted item categories.Once the desired fields 52 are populated, status of account field 56 ischanged from “non-activated” to “activated.”

At 406, distribution agency 12 issues voucher 40 to recipient 14. In oneembodiment, during issuance of voucher 40 to recipient 14, distributionagency 12 populates recipient identification data field 64 in account50, if recipient identification data field 64 was not previouslypopulated. In one embodiment, no recipient identification data field 64is included in account 50. Once presented with voucher 40, recipient 14is able to use voucher 40 toward the purchase of approved items fromredemption organization 16. In one embodiment, at 408, distributionagency 12 monitors use of voucher 40 after voucher 40 is distributed torecipient 14. Distribution agency 12 may monitor voucher use via reportsgenerated by processor 26, as will be further described below.

In one embodiment, at 410, distribution agency 12 adds additional valueto voucher 40 by accessing account 50. For example, after issuingvoucher 40, distribution agency 12 may add a predetermined amount, suchas $500, to the financial balance field 58 at the beginning of eachmonth. In some instances, at 412, distribution agency 12 recaptures anyunredeemed financial balance on voucher 40 after recipient 14 use ofvoucher 40 or upon the passing of an expiration date or other occurrencespecified in expiration date field 62 of account 50. In one embodiment,method 400 does not include one or more of operations 408, 410, and 412.The method 400 is repeated as desired for a plurality of recipients 14.

FIG. 5 is a flow chart illustrating one embodiment of a method ofredeeming vouchers generally indicated at 500 and is described withadditional reference to the embodiments of FIGS. 1, 2, and 3. At 502,redemption organization 16, more particularly a cashier for redemptionorganization 16, receives voucher 40 from recipient 14 during atransaction. In one embodiment, voucher 40 is received before, after, orduring the scanning or other method of entering items 20 to be purchasedby recipient 12 into POS terminal 22 at 504. At 506, account 50 linkedto voucher 40 is accessed by redemption organization 16 by scanning orotherwise reading account identifier 46 of voucher 40 into POS terminal22, which is coupled with management database 24 storing account 50. Inone embodiment, POS terminal 22 is coupled with management database 24via a networked or direct connection. Account identifier 46 is usedsimilar to an address to locate and access the appropriate account 50.Once account 50 is accessed at 506, POS terminal 22 has access to atleast some of account fields 52 and processes use of voucher 50 per thevoucher terms of use defined therein. In view of the above, POS terminal22 coupled with management database 24 is one example of means foraccessing account 30 using account identifier 46.

For example, at 508, voucher status field 56 is examined to determine ifvoucher 40 is activated. If voucher 40 is not activated, it is anindication that voucher 40 may have been stolen or wrongfullyappropriated by the current bearer of voucher 40. Accordingly, ifvoucher 40 is not activated, then at 510, redemption organization 16denies use of voucher 40 toward the purchase of items 20. If voucher 40is activated, method 500 continues to operation 512.

At 512, expiration date field 62 of account 50 is examined to determineif voucher 40 has expired for any reason. If voucher 40 has expired,then at 510, redemption organization 16 denies use of voucher 40 towardthe purchase of items 20. If voucher 40 has not expired, method 500continues to operation 514. In one embodiment, operation 512 is omittedfrom method 500.

At 514, financial balance field 58 of account 50 is examined todetermine if voucher 40 has any remaining balance to be applied towardthe purchase of items from redemption organization 16. If it isdetermined that no available balance remains on voucher 40, then at 510,redemption organization 16 denies use of voucher 40 toward the purchaseof items 20. If it is determined that an available balance remains onvoucher 40, method 500 continues to operation 516.

At 516, recipient identification field 64 of account 50 is examined inview of identification information, such as a name, address, telephonenumber, social security number, driver's license number, etc., presentedto POS terminal 22 directly or via a cashier. If the informationprovided by the voucher bearer fails to match information stored torecipient identification field 64, then at 510, redemption organization16 denies use of voucher 40 toward the purchase of items 20. If theinformation provided by the bearer of voucher 40 matches informationstored to recipient identification field 64, then method 500 continuesto operation 518. In one embodiment, operation 516 is omitted frommethod 500. Although generally described and illustrated as occurringsequentially from operation 508 to operation 516, in one embodiment,operations 508, 512, 514, and 516 may be performed in any order orsubstantially simultaneously. Moreover, other operations may be added toor substituted for any of operations 508, 512, 514, and 516.

At 518, the available balance on voucher 40 (as determined at 512) isapplied toward the purchase of approved items 20 from redemptionorganization 16. More specifically, POS terminal 22 compares thecontents of approved items field 60 to the items scanned for purchase at504. If any of the scanned items falls within the designation ofapproved items in field 60, then POS terminal 22 applies the availablebalance of voucher 40 toward the purchase of such items. Accordingly,POS terminal 22 in communication with management database 24 is oneexample of means for determining whether items to be purchased areapproved items. At 518, POS terminal 22 automatically regulates voucheruse to prevent use of voucher 40 for amounts over the financial balanceindicated by account 50.

At 520, one or more account fields 52 are updated. In particular, thetotal cost of approved items purchased with voucher 40 is subtractedfrom the financial balance in field 58 such that the financial balancefield 58 represents the current available balance of voucher 40. Forexample, if financial balance field 58 indicated a voucher availablebalance of $500 at 512, and if at 516, the balance was applied toward$350 of allowable items, then the financial balance field 58 is updatedat 520 to indicate a new available balance of $150. Accordingly, POSterminal 22 is communication with management database 24 is one exampleof means for applying voucher 40 toward a cost of items in a purchase.

In one embodiment, transaction detail field 66 is also updated at 520.For example, the details of the voucher transaction including suchinformation as generally or specific item descriptions, the item cost,and any other information relating to the approved items purchased withvoucher 40 are logged to transaction detail field 66 for subsequentreview by distribution agency 12. POS terminal 22 in communication withtransaction detail field 66 is one example of means for collecting dataabout the purchase and for storing the collected data. In oneembodiment, although redemption organization 16 can write to transactiondata field 66, transaction data field 66 is only readable bydistribution agency 12. Any other fields 52 are also updated asnecessary or desired.

Method 500 illustrates that enforcement of voucher use is automaticallyeffectuated by POS terminal 22 and the associated electronic network ofredemption organization 16, which decreases the chance of error ascompared to conventional systems where the cashier was entrusted withpolicing voucher use.

FIG. 6 illustrates one embodiment of a method of voucher managementgenerally indicated at 600. Method 600 is described with reference toFIGS. 1 and 3. In one embodiment, method 600 is performed over network18, such as an intranet or the Internet. More specifically, in oneembodiment, redemption organization 16 provides and services a websiteaccessible by distribution agency 12, which supports performance ofmethod 600 by distribution agency 12. Accordingly, the website includesany suitable user graphical interfaces for presenting the variousoperations of method 600 and associated data stored in managementdatabase 24 as described below to distribution agency 12.

At 602, distribution agency 12 logs-in to the website provided byvoucher administrator 38 (FIG. 2) of redemption organization 16 tomanage voucher use. In particular, an individual associated withdistribution agency 12 logs-in with a user name and password, which maybe a mix of alphanumeric characters, a biometric characteristic, orother suitable password. Use of a log-in generally decreasesunauthorized use of the management website. Following log-in at 602,distribution agency 12 is able to manage account profile 604, manageissued vouchers 606, and/or order additional voucher 608.

At 604, distribution agency 12 manages the associated distributionagency profile stored to distribution agency profile storage module 34(FIG. 2) of redemption organization 16. In one embodiment, eachdistribution agency profile includes information to facilitate theworkings of voucher system 10, including communication betweendistribution agency 12 and redemption organization 16. In oneembodiment, managing a distribution agency profile at 604 includes oneor more of editing distribution agency contact information at 610,managing or editing sub-users for distribution agency at 612, managingfinances at 614, and categorically defining approved items lists at 616.

Editing contact information at 610 includes updating or adding one ormore physical addresses, email addresses, phone numbers, contact names,etc. where vouchers 40, billings, or other information can be sent todistribution agency 12. Managing or editing sub-users at 612 definesindividuals associated with distribution agency 12 and user names andpasswords configured to be used by those individuals to manage thevoucher program of the distribution agency 12. In one embodiment, at610, different sub-users are assigned different access levels. Forexample, one access level may only allow a sub-user to perform oneoperation of 604, 606, and 608.

At 614, distribution agency 12 reviews finances with regard to vouchers40, pays voucher bills, etc. For instance, at 614, an account of themoney placed on activated cards by distribution agency 12 is tabulatedalong with fees owed to redemption organization 16, if any, for theredemption of vouchers 40. In one embodiment, managing finances at 614may include cross-referencing a credit account offered by redemptionorganization 16.

At 616, distribution agency 12 is able to define approved itemcategories or restricted item lists for subsequent use in issuingvouchers 40 to recipients 14. In particular, approved and/or restricteditems may be grouped into departmental categories such as food,clothing, alcohol, electronics, pharmaceutical, etc. In one embodiment,category definitions may be based upon the type or relief being offered.For example, a category of approved and/or restricted items may bedefined for poverty relief, disaster assistance, or any other suitablecategory. By defining categories at 616, subsequent approved itemdefinitions for individual vouchers 40 can more easily and quickly beidentified during voucher activation.

At 606, distribution agency 12 manages issued vouchers 40. Issuedvouchers 40 are any vouchers 40 received from redemption organization 16or other supplier that have not been activated by distribution agency 12or any other party. Managing issued vouchers 40 at 606 may include oneor more of monitoring issued and non-activated vouchers 40 at 620,activating issued vouchers at 622, and monitoring activated vouchers 40at 624.

Monitoring issued and non-activated vouchers at 620 generally includesviewing a list that accumulates the relevant information aboutnon-activated vouchers 40. In one example, database processor 26 (FIG.2) of redemption organization 16 generates as list based on accounts 50stored in management database 24. The list includes a listing of accountidentifiers 46 of issued but non-activated vouchers 40 as well as anyrelevant information from account fields 52, such as a current voucherbalance, etc. By viewing this list, distribution agency 12 can evaluateif additional vouchers 40 should be ordered from redemption organization16, etc. In one embodiment, the listing of issued but non-activatedvouchers 40 can be filtered or sorted and presented via databaseprocessor 26 to distribution agency 12 in any suitable manner asdictated by distribution agency 12.

At 622, distribution agency 12 is able to activated previously issuedvouchers 40. In one embodiment, vouchers 40 can be selected foractivation from the list viewed at 620 or by entering individual accountidentifiers 46 into the website. Distribution agency 12 activatesvouchers 40 in a manner similar to that described above for operation404 of method 400 illustrated in FIG. 4. In one embodiment, vouchers 40are activated over network 18 (FIG. 1) via the website supported byredemption organization 16. In one embodiment, vouchers 40 are activatedwith redemption organization 16 over a telephone connection.

Monitoring activated vouchers 40, at 624, includes viewing a listing ofthe account identifiers 46 corresponding to vouchers 40, and therebyaccounts 50, that have been activated as well as any relevantinformation from account fields 52 associated with the listed accountidentifiers 46 as generated by database processor 26 in view ofmanagement database 24. For example, listings of activated vouchers 40may include one or more of the financial balance of each voucher 40, adesignation of whether each voucher 40 has been redeemed, a designationof whether there is transaction detail for each voucher 40, a listing ofany transaction details for each voucher 40, etc. In one embodiment, thelisting of activated vouchers 40 can be filtered or sorted by databaseprocessor 26 in any suitable manner as dictated by distribution agency12.

In one embodiment, individual account identifiers 46 can be selectedfrom the listing provided at 624, and the associated account 50 can beadditionally managed. For example, once an individual account identifier46 is selected a new graphical interface may be presented todistribution agency 12 that displays more detailed information about theassociated account 50. In one embodiment, while in the detailed accountmode, value can be added to account 50 at 626 and/or funds can berecaptured from account 50 at 628. In one example, funds mayautomatically be added to account 50 at the expiration of a given timeperiod or occurrence of any other triggering event and/or funds may beadded by action of distribution agency at 626. In one embodiment, aplurality of account identifiers 46 may be selected from the activatedaccount identifier list and funds may be added to accounts 50 associatedwith the plurality of account identifiers 46 at one time.

Similarly, funds can be recaptured from accounts 50 having residualbalances after the expiration date has passed or other triggering eventhas occurred. Recapturing residual funds allows distribution agency 12to reclaim any financial balance remaining on voucher 40 after use. Uponrecapture at 628, the credit account of distribution agency 12 may becredited or a refund may be issued. In one embodiment, funds from aplurality of accounts 50 are simultaneously recaptured by selecting anassociated plurality of account identifiers from the listing ofactivated vouchers. As such, the website operated by database processor26 is one example of means for refunding a non-redeemed value of voucher40. Listings regarding vouchers viewed by distribution agency 12 duringone of operations 604 and 606 may be generated by processor 26 inreal-time or based on previously generated reports saved to generatedreports storage module 36 (FIG. 2) of management database 24.

At 608, distribution agency 12 can order additional vouchers 40 fromredemption organization 16 or other supplier. In one embodiment, anorder includes how many vouchers 40 are being ordered, what distributionagency 12 is placing the order, and any other specifics regarding theorder, such as any preset financial balance, expiration date, etc. forany of vouchers 40. In one embodiment, additional vouchers are orderedat 608 via the website operated by redemption organization 16 or othervoucher supplier or over the telephone network. In one embodiment,following completion of an operation 604, 606, or 608 one of the otheroperations 604, 606, and 608 is completed.

At 630, after operation 604, 606, and/or 608 are completed as desired bydistribution agency 12, distribution agency 12 logs off of the websiteor other portal accessing management database 24 (FIG. 2). It should benoted that any website operated by redemption organization 16 or otherparty by support operations 604, 606, and 608 with various graphicalinterfaces as will be apparent to those of skill in the art.

FIG. 7 illustrates a block diagram of a voucher system 700 similar tovoucher system 10 of FIG. 1 but additionally including a voucheradministrator 702. Voucher administrator 702 communicates withdistribution agency 12 and redemption organization 16′ either directlyor via network 18. In one embodiment, voucher administrator 702 suppliesvouchers 40 to distribution agency 12, maintains management database 24and processor 26, and supports method 600 and any associated website ornetwork. In this embodiment, redemption organization 16′ optionally doesnot include a voucher administrator 38, processor 26, or database 24 asdescribed above and does not provide distribution agency 12 with vouchermanagement support. Redemption organization 16′ is in remotecommunication with voucher administrator 702 to access at least aportion of account fields 52 to update such fields during or after atransaction with POS terminal 22 involving an associated voucher 40.

In this embodiment, voucher administrator 702 optionally is not bedirectly linked to a particular redemption organization 16′. In oneembodiment, voucher 40 provided by voucher administrator 702 todistribution agency 12 may be redeemed by recipient 14 at any one of aplurality of redemption organizations 16′ each having electronic accessto voucher accounts 50 via network 18. In one example, each voucheraccount stored by voucher administrator 702 may include an additionalfield to be populated by distribution agency 12 that designates one ormore of the available redemption organizations 16′ that can redeemvoucher 40 toward the purchase of items. In one embodiment, voucheradministrator 702 is optionally part of distribution agency 12.

Although the invention has been described with respect to particularembodiments, such embodiments are for illustrative purposes only andshould not be considered to limit the invention. Various alternativesand changes will be apparent to those of ordinary skill in the art.Other modifications within the scope of the invention in its variousembodiments will be apparent to those of ordinary skill.

1. A system for managing voucher use, the system comprising: a databasestoring an account defining at least one approved item available forpurchase and a financial balance; a voucher including an identifierlinking the voucher to the account; and a processor in communicationwith the database and adapted to use the identifier to access theaccount, wherein the processor is adapted to determine if an itemselected for purchase is an approved item and to apply at least aportion of the financial balance toward the purchase of the selecteditem only if the selected item is an approved item.
 2. The system ofclaim 1, wherein the processor is adapted to substantially preventapplication of the financial balance toward any selected items that arenot approved items.
 3. The system of claim 2, wherein the accountdefines the at least one approved item by non-inclusion of the at leastone approved item in a restricted item definition included within theaccount.
 4. The system of claim 1, wherein the account includes atransaction details field including a listing of the selected itemspurchased with the voucher.
 5. The system of claim 1, wherein theaccount includes expiration data specifying one of a date and anoccurrence upon which any residual financial balance can be recaptured.6. The system of claim 1, wherein the processor is a redemptionprocessor, the system further comprising: an administrator processor incommunication with the database, the administrator processor beingconfigured to support a website based upon the database, wherein thewebsite is configured to facilitate access to and customization of theaccount.
 7. The system of claim 6, wherein the website is configured toenable ordering of additional vouchers each linked to an associatedaccount stored on the database.
 8. The system of claim 6, wherein theaccount includes a transaction details field including a listing of allselected products purchased with the voucher, the transaction detailsfield being accessible via the website.
 9. The system of claim 6,wherein the administrator processor is configured to enable access tothe account via the website and is configured to enable use of thewebsite to define the at least one approved item and to define thefinancial balance of the account.
 10. The system of claim 6, wherein theadministrator processor is configured to process orders for additionalvouchers to be delivered to a distribution agency, to generate a billfor the additional vouchers, and to credit the distribution agency forrecaptured residual financial balances of the additional vouchers. 11.The system of claim 1, wherein the voucher is a stored-value card. 12.The system of claim 1, wherein the processor is included in apoint-of-sale (POS) terminal.
 13. The system of claim 12, wherein thePOS terminal includes an electronic reader coupled with the processorand configured to read the identifier of the voucher.
 14. A system forredeeming a financial transaction instrument toward a purchase of items,the system comprising: means for reading an identifier of a financialtransaction instrument presented at a point-of-sale; means for accessingan account from the point-of-sale using the identifier, wherein theaccount defines approved items; means for determining whether items tobe purchased are approved items as defined by the account; and means forapplying the financial transaction instrument toward a cost of theapproved items to be purchased.
 15. The system of claim 14, furthercomprising means for preventing use of the financial transactioninstrument toward a cost of items in the purchase determined not to beallowable items by the means for determining.
 16. The system of claim14, further comprising means for collecting data about the purchase andother purchases made with the financial transaction instrument and forstoring the collected data to the account.
 17. The system of claim 14,further comprising means for refunding a non-redeemed value of thefinancial transaction instrument after the financial transactioninstrument has been applied toward the cost of the approved items.
 18. Amethod for redeeming a financial transaction instrument toward apurchase of items, the system comprising: reading an identifier of afinancial transaction instrument presented at a point-of-sale; accessingan account from the point-of-sale using the identifier, wherein theaccount defines approved items; determining whether items selected forpurchase are approved items as defined by the account; and applying thefinancial transaction instrument toward a cost of the selected itemsdetermined to be approved items.
 19. The method of claim 18, furthercomprising: preventing use of the financial transaction instrumenttoward a cost of selected items determined not to be approved items. 20.The method of claim 18, further comprising: collecting data about theapplication of the financial transaction instrument toward the cost ofthe selected items determined to be approved items, wherein the dataincludes details about the selected items; storing the collected data tothe account.
 21. The method of claim 18, wherein the account defines afinancial balance, and applying the financial transaction instrumentincludes applying up to all of the financial balance toward the cost ofthe selected items determined to be approved items.
 22. The method ofclaim 21, further comprising: reporting the application of the financialtransaction instrument toward the cost to the account; and updating thefinancial balance defined by the account based on the cost of theselected items determined to be approved items.
 23. The method of claim21, further comprising: refunding the financial balance, if any,remaining after application of the financial transaction instrumenttoward the cost.
 24. The method of claim 18, further comprising:determining whether the financial transaction instrument is active,wherein determining whether items selected for purchase are approveditems and applying the financial transaction instrument toward the costonly occur when the financial transaction instrument is determined to beactive.
 25. The method of claim 18, further comprising: permittingaccess to the account via a website, wherein the website is configuredto allow a distribution agency to order additional financial transactioninstruments and to manage accounts associated with the additionalfinancial transaction instruments.